Deploy tokens can’t be used with the GitLab public API. For details, see Deploy Tokens. You can use an OAuth2 token to authenticate with the API by passing it in either the access_token parameter or the Authorization header. Read more about GitLab as an OAuth2 provider.

The GitLab API supports the application/json content type by default, though some API endpoints also support text/plain. In GitLab 13.10 and later , API endpoints do not support text/plain by default, unless it’s explicitly documented. Introduced in GitLab 14.9. REST API requests can be detected as spam.

Automatically creating Issues leveraging Gitlab CI and API In order to create issues using Gitlab API we will use the Issues API an example of that can use the following cURL command:

GitLab supports bot users such as the alert bot or the support bot . You can exclude the following types of internal users from the users’ list with the exclude_internal=true parameter ( introduced in GitLab 13.4): However, this action does not exclude bot users for projects or bot users for groups.